Collection Of Common Malfunctions And Self-Troubleshooting Steps For Malaysia-based Lighthouse Cloud Servers

This article provides practical and actionable steps for self-troubleshooting for operations personnel and developers running lightweight cloud servers in Malaysia. This article focuses on "Common Malfunctions of Malaysian Lighthouse Cloud Servers and a Collection of Self-Troubleshooting Steps." It emphasizes quick identification, low-risk repairs, and reporting when necessary, with the aim of improving fault response efficiency and system availability.

The network connection has been interrupted: Troubleshooting approach and common commands

When encountering issues with external access or internal network connectivity, it is recommended to first use tools such as ping or traceroute (or tracert) on the server to check the connection. This will help determine whether the disruption is caused by local routing settings or the upstream service provider. Check the network interface configuration, default gateway, and routing table (using commands like `ip addr` and `ip route`). If any changes have been made, restart the network services and log these changes for tracking purposes.

Diagnosis and Repair of DNS Resolution Issues

DNS-related issues often manifest as either the inability to resolve a domain name or resolving it to the wrong IP address. First, use dig or nslookup to verify the resolution results and check whether /etc/resolv.conf or the system’s DNS configuration has been accidentally altered. If the parser is unavailable, you can temporarily switch to public DNS for verification. If necessary, clear the local cache and synchronize the DNS records with the hosting platform.

Self-help steps for SSH/remote login failures

Remote login failures may be caused by issues with the key, port, or SSHD configuration. Access the console to check the status and logs of the sshd service (using journalctl or /var/log/auth.log) to confirm the SSH port settings, firewall rules, and authentication methods in use. In case of configuration errors, you can switch to single-user mode or use the cloud platform console to modify the configuration file and then restart the service.

Troubleshooting disk space and I/O performance issues

Full disk space or high I/O levels can cause application malfunctions. Use `df -h` to check partition usage, `du -sh` to identify large files, and `lsof` to determine which file handles are being occupied. Clean up or rotate temporary files and logs as needed, expand disk capacity or adjust I/O limits when necessary. At the same time, monitor real-time statistics from tools like iostat and iotop to identify any bottleneck processes.

Troubleshooting methods for high CPU and memory usage

When the server is under heavy load or running out of memory, use tools like top, htop, or ps aux --sort=-%mem/-%cpu to identify the processes that are consuming excessive resources. Check whether it was triggered by sudden traffic, a memory leak, or a backup task. You can start by restricting or restarting abnormal processes, configuring appropriate daemons and monitoring alerts, and considering adjusting application parameters or implementing scaling solutions to reduce the load.

Handling of Service Unavailability Due to Firewall and Security Group Configurations

When the service is unavailable, it is necessary to check the operating system's firewall (iptables/nftables/firewalld) as well as the cloud-based security group rules. Ensure that the inbound and outbound port numbers, protocols, and source address allowlists are set correctly. During debugging, ports can be temporarily opened to verify connectivity. After correcting the rules, the changes should be recorded, and the principle of minimum privilege should be re-established to ensure security.

Common approaches to dealing with failures in snapshotting, backup, and restoration processes

Backup or snapshot failures may be caused by insufficient space, concurrency limits, or permission issues. Check the backup task logs, the status of the target storage, and the permission settings to ensure that disk consistency is maintained before taking the snapshot, or that application freezing measures have been properly implemented. In case of recovery failures, first verify the integrity of the data in an isolated environment, and then proceed with the recovery steps layer by layer, verifying the service's functionality at each stage.

Summary and Recommendations

In summary, “Collection of Common Issues and Self-Troubleshooting Steps for Malaysia’s Lighthouse Cloud Servers” provides diagnostic procedures for key scenarios involving networking, DNS, SSH, disks, CPU/memory, firewalls, and backups. It is recommended to establish monitoring alerts and change logs, conduct regular recovery process drills, and promptly provide detailed diagnostic information to cloud platform support when issues cannot be resolved independently, in order to accelerate issue identification and resolution.